NTISthis.com

Evidence Guide: ICTPRG510 - Maintain custom software

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG510 - Maintain custom software

What evidence can you provide to prove your understanding of each of the following citeria?

Determine the software fault to be corrected

  1. Collect and review the software fault details from sources
  2. Obtain technical data to assist in identifying the problem
  3. Clarify nature of the problem with appropriate person where necessary
Collect and review the software fault details from sources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain technical data to assist in identifying the problem

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clarify nature of the problem with appropriate person where necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and isolate the fault

  1. Review program documentation for specific modules in order to pinpoint problem areas
  2. Review the source code for logic errors
  3. 2.3 Read manuals, help files and 'read me files' to determine if there is a known fix
  4. Undertake additional testing to identify or duplicate fault
  5. Escalate the difficult faults that cannot be identified
Review program documentation for specific modules in order to pinpoint problem areas

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the source code for logic errors

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Undertake additional testing to identify or duplicate fault

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Escalate the difficult faults that cannot be identified

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design a fix for the fault

  1. Ensure that the requirements needed to fix the fault are understood by the client
  2. Consider alternative options and choose the most effective solution
  3. Consider the possible impact of the fix on other parts of the system
  4. Document the changes according to the organisational guidelines
Ensure that the requirements needed to fix the fault are understood by the client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider alternative options and choose the most effective solution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider the possible impact of the fix on other parts of the system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes according to the organisational guidelines

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Carry out the fix to the software

  1. Identify, and obtain, access to the appropriate software development tools, source code, and libraries
  2. Construct the appropriate code to correct the fault, according to organisational and programming standards
  3. Compile, or regenerate, the code for changed programs and the associated modules
  4. Correct, and resubmit, the code until error free
  5. Document the changes, according to organisational and programming standards
Identify, and obtain, access to the appropriate software development tools, source code, and libraries

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Construct the appropriate code to correct the fault, according to organisational and programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compile, or regenerate, the code for changed programs and the associated modules

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Correct, and resubmit, the code until error free

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes, according to organisational and programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the fix and associated system areas

  1. Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere
  2. Request users to perform acceptance testing and record outcomes
Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Request users to perform acceptance testing and record outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Hand over to systems operations area

  1. Update the documentation to reflect all the changes made
  2. Confirm acceptance by systems operations and arrange for sign-off, according to procedures
Update the documentation to reflect all the changes made

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the software fault to be corrected

1.1 Collect and review the software fault details from sources

1.2 Obtain technical data to assist in identifying the problem

1.3 Clarify nature of the problem with appropriate person where necessary

2. Identify and isolate the fault

2.1 Review program documentation for specific modules in order to pinpoint problem areas

2.2 Review the source code for logic errors

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

2.4 Undertake additional testing to identify or duplicate fault

2.5 Escalate the difficult faults that cannot be identified

3. Design a fix for the fault

3.1 Ensure that the requirements needed to fix the fault are understood by the client

3.2 Consider alternative options and choose the most effective solution

3.3 Consider the possible impact of the fix on other parts of the system

3.4 Document the changes according to the organisational guidelines

4. Carry out the fix to the software

4.1 Identify, and obtain, access to the appropriate software development tools, source code, and libraries

4.2 Construct the appropriate code to correct the fault, according to organisational and programming standards

4.3 Compile, or regenerate, the code for changed programs and the associated modules

4.4 Correct, and resubmit, the code until error free

4.5 Document the changes, according to organisational and programming standards

5. Test the fix and associated system areas

5.1 Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

5.2 Request users to perform acceptance testing and record outcomes

6. Hand over to systems operations area

6.1 Update the documentation to reflect all the changes made

6.2 Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the software fault to be corrected

1.1 Collect and review the software fault details from sources

1.2 Obtain technical data to assist in identifying the problem

1.3 Clarify nature of the problem with appropriate person where necessary

2. Identify and isolate the fault

2.1 Review program documentation for specific modules in order to pinpoint problem areas

2.2 Review the source code for logic errors

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

2.4 Undertake additional testing to identify or duplicate fault

2.5 Escalate the difficult faults that cannot be identified

3. Design a fix for the fault

3.1 Ensure that the requirements needed to fix the fault are understood by the client

3.2 Consider alternative options and choose the most effective solution

3.3 Consider the possible impact of the fix on other parts of the system

3.4 Document the changes according to the organisational guidelines

4. Carry out the fix to the software

4.1 Identify, and obtain, access to the appropriate software development tools, source code, and libraries

4.2 Construct the appropriate code to correct the fault, according to organisational and programming standards

4.3 Compile, or regenerate, the code for changed programs and the associated modules

4.4 Correct, and resubmit, the code until error free

4.5 Document the changes, according to organisational and programming standards

5. Test the fix and associated system areas

5.1 Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

5.2 Request users to perform acceptance testing and record outcomes

6. Hand over to systems operations area

6.1 Update the documentation to reflect all the changes made

6.2 Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Evidence of the ability to:

effectively maintain custom software

apply a fix that works

deploy a possible range of solutions to produce the same results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the concepts relating to analysing a system performance compared with the system’s current functionality

describe the processes and procedures relating to testing software systems

describe current industry-accepted hardware and software products, as they relate to system maintenance

specify the programming code required for the project

describe the program documentation required

describe the impact of changes on applications and systems

identify and summarise the programming standards relating to custom software.